From: Colin Walters <walters@verbum.org>
Date: Fri, 20 Jun 2014 14:11:42 +0000 (-0400)
Subject: docs: overview: Explicitly call out dpkg/rpm
X-Git-Tag: archive/raspbian/2022.1-3+rpi1~1^2~1168
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=1b1e3a592eeeee9da351837d06c70cd506a9a5a7;p=ostree.git

docs: overview: Explicitly call out dpkg/rpm

To be more clear that we don't handle "inventory".
---

diff --git a/doc/overview.xml b/doc/overview.xml
index 79763b5e..f2273068 100644
--- a/doc/overview.xml
+++ b/doc/overview.xml
@@ -40,11 +40,13 @@
       <emphasis>complete</emphasis> (bootable) filesystem trees.  It
       has no built-in knowledge of how a given filesystem tree was
       generated or the origin of individual files, or dependencies,
-      descriptions of individual components.  This means that, for
-      example, if you are distributing software which is licensed
-      under the GNU General Public License, the burden lies with the
-      tool generating these filesystem trees to ensure sufficent
-      metadata is included for compliance.
+      descriptions of individual components.  Put another way, OSTree
+      only handles delivery and deployment; you will likely still want
+      to include inside each tree metadata about the individual
+      components that went into the tree.  For example, a system
+      administrator may want to know what version of OpenSSL was
+      included in your tree, so you should support the equivalent of
+      <command>rpm -q</command> or <command>dpkg -L</command>.
     </para>
     <para>
       The OSTree core emphasizes replicating read-only OS trees via